User interface for dynamic generation of tournament brackets

ABSTRACT

The present disclosure describes an administration system which facilitates efficient setup, organization, and maintenance of tournaments, including league games. In particular, the administration system provides a user-friendly, intuitive and efficient-to-use interface for organizing tournaments and tournament brackets. The user interfaces and methods described provide tournament organizers and administrators with the ability to quickly and dynamically build custom tournament brackets of virtually any desired depth and configuration. The administration system, and in particular the tournament bracket management user interfaces, enable tournament administrators to focus on the task of building a custom tournament bracket structure quickly, while also automatically handling the minute logistics underlying the tournament such as when and where games are to be played.

BACKGROUND

Tournament organization and administration can often be a time-consumingand manual task, involving considerable management and overhead. Thelogistics of managing who (from individual players, teams, and divisionsto other groupings), what, where, when, and how can be exponentiallycomplex as the number of these variables increases. One area that can beparticularly cumbersome for league and tournament organizers andadministrators is in managing schedules. The typical administrator facesconsiderable challenges to managing games quickly and efficiently, fromsetting up regular season games in a manner that fairly balances agelevels, skill sets, and other factors for hundreds of players and teams,to organizing balanced tournaments.

SUMMARY

The present disclosure describes a bracket administration system whichfacilitates efficient setup, organization, and maintenance of leaguegames and tournaments. The bracket administration system provides auser-friendly, intuitive and efficient-to-use interface for organizingbrackets for regular season or league play, and for tournaments whichmay be stand-alone or be based in part on regular season or league playstandings. The user interfaces and methods described provide organizersand administrators with the ability to quickly and dynamically buildcustom tournament brackets of virtually any desired depth andconfiguration. The bracket administration system, and in particular thebracket management user interfaces, enable league and tournamentadministrators to focus on the task of building a custom tournamentbracket structure quickly, while also automatically handling the minutelogistics underlying the tournament such as when and where games are tobe played. In some cases the bracket administration system mayautomatically determine which teams (or individuals, depending upon thesport) will play in a given game or match of a tournament based on theteam or individual's placement or standing at the end of a season (or atthe point in time just before the tournament is scheduled to begin).

The bracket management user interface gives administrators the option toconfigure specific teams (e.g., Team A plays Team B in the first roundof a tournament, and the winner plays Team C in the second round) orplacements (e.g., the #1 team in a grouping, such as a Division orFlight, based on standings before the tournament begins, plays the #2team in the grouping; the actual teams playing may be unknown or “to bedetermined” when the tournament begins). Traditional approaches tobracket management often include manual data entry in a spreadsheet ortable, a process that is time-consuming and more difficult to adjust orupdate. One benefit of the bracket management user interface describedherein is that once a bracket hierarchy has been constructed by anadministrator, the administration system can automatically populate,generate or update a tournament schedule with minimal or no furtherinput by the user.

Neither this summary nor the following detailed description purports todefine the scope of protection. The scope of protection is defined bythe claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram depicting an illustrative network environmentin which a sport league administration system may operate.

FIG. 2 illustrates an example user interface for dynamically generatinga tournament bracket using the sport league administration system ofFIG. 1.

FIGS. 3A and 3B illustrate an example of using the tournament bracketmanagement user interface to add a game or branch to a tournamentbracket using the sport league administration system of FIG. 1.

FIGS. 4A and 4B illustrate an example of using the tournament bracketmanagement user interface to remove a game or branch from a tournamentbracket using the sport league administration system of FIG. 1.

FIGS. 5A and 5B illustrate an example of using the tournament bracketmanagement user interface to move a game or branch in a tournamentbracket using the sport league administration system of FIG. 1.

FIGS. 6A and 6B illustrate an example of using the tournament bracketmanagement user interface to add a team or placement to a game in atournament bracket using the sport league administration system of FIG.1.

FIG. 7 illustrates an example user interface for dynamically generatingtwo or more tournament brackets using the sport league administrationsystem of FIG. 1.

FIG. 8 illustrates a detail view of a user interface element for a gamein a tournament which may be displayed as part of a tournament bracketmanagement user interface using the sport league administration systemof FIG. 1.

FIG. 9 is a logical flow diagram of an embodiment of a process forbuilding one or more tournament brackets and generating a tournamentschedule using the sport league administration system of FIG. 1.

FIG. 10 is a logical flow diagram of an embodiment of a process forconfiguring one or more tournament brackets and generating a tournamentschedule using the sport league administration system of FIG. 1.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

Overview

The bracket management features described herein may be part of astand-alone tournament management application, or integrated as part ofa larger league administration system. For ease of explanation, thebracket management features and user interfaces are illustrated anddescribed herein in the context of a league administration system thatincludes other league administration features. As will be recognized,the disclosed features are also applicable to bracket creation andmanagement for non-league tournaments and brackets. Further, thedisclosed features are also applicable to tournaments and competitionsinvolving non-sports activities such as chess, spelling competitions,etc.

The term “tournament,” as used herein, is intended to encompass bothleague-based and non-league-based competitive events. For example, atournament may consist of (1) regular season games played within aleague, (2) league playoff games, or (3) a competitive event that is notpart of a league.

In one embodiment a tournament bracket management user interface (“UI”)provides a user, such as a league organizer or administrator, with amenu of placements or standings based on or generated from games playedduring a regular season. During the regular season, players may beplaced on teams according to a variety of criteria (e.g., age, skilllevel, sex, physical attributes, and so on); teams may be placed ingroups such as Divisions, also according to the same or other criteria;and within Divisions, teams may further be placed into sub-groups suchas Flights, also according to the same or other criteria. Flightorganization may be beneficial to encourage participation and balancecompetition, particularly for large Divisions in which skill levels varywidely within the same age group. Thus, during the regular season, asteams play games within their Division and/or Flights, they mayaccumulate placement standings. These placement standings may then beaccessed by or provided to the tournament bracket management system ormodule, although the actual placement standings may not be displayed inthe bracket manager user interface.

The tournament bracket management user interface provided by the leagueadministration system described herein enables the user to, for example,begin by selecting a league division for which a tournament is to becreated, edited, or managed. The system enables the user to add as manytournament brackets to the tournament as desired. For each tournamentbracket, the tournament bracket management user interface providescontrols for the user to quickly and easily add games to a brackethierarchy (e.g., a tree diagram), for example by selecting a plus iconuser interface element, symbol or other similar indicator associatedwith games in the bracket. In response to selection of the “plus” userinterface element coupled to a selected game, the tournament bracketmanagement user interface automatically adds a new game in a tournamentround preceding the tournament round of the selected game. The winner ofthe newly added game would then be placed in the selected game toproceed through the tournament. The user can continue to branch games inthis way to build out the tournament bracket to as many levels, orrounds, as desired.

Similarly, for each tournament bracket, the tournament bracketmanagement system and user interface provides controls for the user toquickly and easily remove games from a bracket hierarchy (e.g., a treediagram), for example by selecting a cross or “X” icon user interfaceelement, symbol or other similar indicator associated with games in thebracket. In response to selection of the “X” user interface elementcoupled to a selected game, the tournament bracket management userinterface automatically removes the branch game (or an entire branch ofgames if there are multiple levels games preceding the branch game) ofthe bracket hierarchy preceding or leading into the selected game. Thewinner of the newly added game would then be placed in the selected gameto proceed through the tournament. The user can continue to branch gamesin this way to build out the tournament bracket to as many levels, orrounds, as desired.

The tournament bracket management system and user interface may alsoinclude a bracket/division management menu for the user to furthercustomize the tournament bracket(s). This menu may include, for example,the ability to select a division for tournament editing, the ability toadd additional brackets to a tournament, and the ability to select teamsand/or placements for games in the tournament bracket(s). For example,in one embodiment, the user may configure the teams to play in aselected game by a drag-and-drop user interaction of “dragging” a teamor placement from the menu and “dropping” the selected team or placementonto the selected game. The user can continue to add teams to games inthis way to configure the tournament bracket until teams or placementshave been assigned to each of the entry point games (e.g., games whichhave at least one competing team that is not a winning team from anothergame in the bracket).

The tournament bracket management system and user interface may provideother features and functionality, including, for example, functionalityfor moving games from one round to another round (e.g., to create oreliminate a bye game or round), and zoom controls to enable zooming inor out of the tournament bracket view (a feature of particular benefitif the tournament bracket has multiple levels and/or a large number ofgames).

Once the league organizer has built and configured the tournamentbrackets, the sport league administration system can then automaticallygenerate a tournament schedule for each bracket. The schedule generationprocess may include automatically determining a field or venue for thegame, and dates and times, and may be based in part on other league dataavailable to the sport league administration system. In someembodiments, the field and date/time attributes may also be manuallyconfigurable by the user via the tournament bracket management userinterface.

The features and user interfaces described herein may be applicable toany type of competitive sport which may be organized into a league,conference, tournament, or similar organization. For simplicity, theexamples of games described herein may only include two teams. However,in some embodiments there may be games which involve more than two teams(e.g., a game of paintball may involve three or more teams, with one ormore “winning” teams eligible to advance to the next round). In thesecases there may be additional placement teams added to each game in atournament bracket. For each additional team, the user would have anadditional option to create a branch leading into that game to determinethe winner(s) from previous rounds to play in the game of more than twoteams. It may also be possible that in some embodiments and/or dependingon the sport, instead of teams the games may only involve a singleplayer (e.g., tennis, wrestling, chess, single player card games such aspoker, etc.). All of the examples shown and described herein areapplicable to such “single player” sports or scenarios, as well assports in which games may involve more than two teams competing for oneor more winning placements to advance to the next round. As used hereinthe terms league administration system and sport league administrationsystem may be used interchangeably.

Example System Architecture

FIG. 1 is a general architecture diagram schematically illustrating anexample of a sport league administration (“SLA”) system 100 thatperforms and provides the tournament bracket generation servicesdescribed herein. The SLA system 100 can include any system capable ofperforming the processes described herein. For example, in theillustrated embodiment of FIG. 1, the SLA system 100 communicates withone or more user computing devices 105 over a network 160. In FIG. 1,the SLA system 100 includes several components such as a leaguemanagement module 110, user interface module 130 and a schedulemanagement module 120. The schedule management module 120 may alsoinclude, for example, a tournament/bracket management module 125. Thesecomponents may also include further components that may not be depictedin FIG. 1. For example, SLA system 100 can also include one or moreservers, e.g., a web server, configured to receive and respond torequests from the user computing devices 105.

The league management module 110 may be configured to, for example,manage various aspects of a sports league including, but not limited to,registration of participants or players, managing seasons, teams,divisions, flights, uniforms, accounts/finances, and other suchadministrative matters related to running a sports league. The schedulemanagement module 120 may be configured to execute various processes andmethods for managing different schedules for a league including viewingor editing a games calendar, scheduling games, organizing flights ordivisions, setting up tournament brackets and managing fields, amongother things. In particular, the tournament bracket management module125 may be configured to execute various processes, such as the process900 described with reference to FIG. 9) and the process 1000 describedwith reference to FIG. 10.

Also shown in FIG. 1, the SLA system 100 may include and/or have accessto one or more data stores or data sources including, for example, aleague data store 140 and a game/scheduling data store 150. The leaguedata store 140 may include data for the league administration system,such as information or data about leagues, conferences, teams andplayers/athletes, coaches, divisions, flights, venues or fields,placements, standings, win/loss records, various statistics about theteams and games, season standings, historical tournament results, and soforth. The game schedule data 150 may include data related to schedules,calendars, matchups or games, tournaments and other similar data relatedto the actual scheduling of games.

Also shown in FIG. 1, a sample user computing device 105 may include auser interface module 107 which may be configured to execute some or allof the processes described herein. This may, for example, enable theuser computing device 105 to provide the tournament bracket creationfeatures to the user of the device, even when the device may be notconnected to the SLA system 100 over the network 160. This may be thecase, for example, if the user computing device 105 does not havewireless access, may not be connected to a cellular network, and soforth. In some embodiments, the SLA system 100 may be a web-based systemthat may be accessed by users using an ordinary web browser. The SLAsystem 100 may be accessible by a league organizer or administrator toperform the bracket management functions described herein. In otherembodiments, the SLA system 100 may also be accessible by anon-administrative users (e.g., players, coaches, etc.) who may havepermission to view tournaments, brackets, game results, and so on, butmay not have access to the bracket management functions provided by theleague administration system.

The user interface module 107 may be configured to, for example,generate one or more user interfaces, such as the user interfacesdescribed herein (e.g., FIGS. 2, 3A, 3B, 4A, 4B, 5A, 5B, 6A, 6B, 7, and8), to provide the tournament bracket features to the user of thedevice. In one embodiment, some or all of the user interfaces and/or UIelements may be generated either by the SLA system 100 and provided tothe user computing device 105, or they may be generated on the usercomputing device 105 via the user interface module 107, or in somecombination thereof.

Example User Interfaces for Generating Tournament Brackets

FIGS. 2, 3A, 3B, 4A, 4B, 5A, 5B, 6A, 6B, 7, and 8 illustrate exampleuser interfaces related to dynamic generation of tournament brackets, asused in one or more embodiments of the SLA system 100. The sample userinterfaces may be displayed, for example, via a web browser (e.g., as aweb page), a mobile application, or a standalone application. However,in some embodiments, the sample user interfaces shown in FIGS. 2, 3A,3B, 4A, 4B, 5A, 5B, 6A, 6B, 7, and 8 may also be displayed on anysuitable computer device, such as a cell/smart phone, tablet,portable/mobile computing device, desktop, laptop, or personal computer,and are not limited to the samples as described herein. The userinterfaces include examples of only certain features that a SLA system100 may provide. In other embodiments, additional features may beprovided, and they may be provided using various different userinterfaces and software code. Depending on the embodiment, the userinterfaces and functionality described with reference to FIGS. 2, 3A,3B, 4A, 4B, 5A, 5B, 6A, 6B, 7, and 8 may be provided by softwareexecuting on the individual's computing device (e.g., via user interfacemodule 107), by a SLA system 100 located remotely that is incommunication with the computing device via one or more networks, and/orsome combination of software executing on the computing device and theSLA system 100. In other embodiments, analogous interfaces may bepresented using audio or other forms of communication. In an embodiment,the interfaces shown in FIGS. 2, 3A, 3B, 4A, 4B, 5A, 5B, 6A, 6B, 7, and8 are configured to be interactive and respond to various userinteractions. Such user interactions may include clicks with a mouse,typing with a keyboard, touches and/or gestures on a touch screen, voicecommands, and/or the like.

FIG. 2 illustrates an example user interface 200 for dynamicallygenerating tournament brackets in one embodiment of the SLA system 100of FIG. 1. As shown in FIG. 2, the bracket manager interface presentsthe user with a view of one or more tournaments and various games thatare organized within the tournament. The user may be able to edit thetournament name for example, via the UI element 201. In this example,the tournament is named “Gold Level Tournament.” Via selection of UIelement 202, the user can also delete the current bracket.

The user interface shown in FIG. 2 includes a menu on the right formanaging brackets for a particular league division (e.g., youth female,ages 6-7, as shown as selected at UI element 204). At UI element 205,the user may have the option to add an additional bracket to thetournament. The user interface for the bracket manager can support asmany brackets as the user would like to add. An example of multiplebrackets shown in the bracket manager is illustrated with reference toFIG. 7. Also shown in the bracket manager menu on the right, UI element206 presents the user with a list of division placements, UI element 207presents a list of flight placements, UI element 208 presents a list ofbracket placements for the tournament bracket(s), UI element 209presents a list of teams, and UI element 210 presents a list ofplacements.

As shown in FIG. 2, the division placements UI element 206 is expandedto display a list of division placements which are eligible forinclusion in this tournament. As will be further described herein, theuser can select a division placement for inclusion in the tournament by,for example, clicking on/selecting, dragging and dropping one of thedivision placements from the list onto a game in the tournament bracket.Thus, for example, as shown in FIG. 2, the user has selected “#3 indivision” and “#4 in division” for Game 001 in Round 1. In otherembodiments, the user may also be able to add flight placements, bracketplacements or specific teams. Division placements may correspond to therankings for this particular division at the end of a season or at thetime the tournament is scheduled to begin. Similarly, the leagueadministrator may have organized various flights as another way ofgrouping the teams for play during a regular season. Thus, the user maywant to configure the tournament based on the placement within variousflights as opposed to placement within certain divisions. This might beparticularly beneficial where a flight is organized or grouped forplayers of similar skill level or age, which may not be reflected at thedivision level.

The bracket placements include, for example, a list of placements thatare generated as the tournament bracket is built out. So, for example,the bracket placements list may include a Loser of Game 001, a Loser ofGame 002, a Loser of Game 003, and so forth for each game currently inthe tournament bracket. Then the user may use these bracket placementsto further develop the tournament bracket, for example, by creatingrunner-up matches, games for third place or consolidation games, andsimilar variations on having the loser of the game play the loser ofanother game to further develop the tournament bracket.

A list of teams in the selected division may also be presented so thatthe user may build the tournament bracket directly by matching certainteams against each other. This may be desirable in some circumstanceswhere the division/placements and/or the flight placements may not bereadily available, or in some instances in which the user may wish tooverride the default behavior of the SLA system 100. For example, if theuser knows that the no. 1 division team has been disqualified forvarious reasons or is no longer eligible to play, then the user may wishto select an alternate team from the teams list to fill in that spot.Finally, the placements selection list may include points that may beassociated with the winner of a given game or tournament bracket. Theseplacement points may be tracked over time by the SLA system 100, suchthat during the course of league play, a tournament, or multipletournaments, the teams/players carry their placement points with them.

Also shown in FIG. 2, the user can build the tournament bracketdynamically and quickly by using the various expansion buttons such asthe one shown at UI element 211. These indicators may be displayed, forexample, to the left of a game and enable the user to create a newbranch off of the preceding game or the base game. As shown in FIG. 2,the user can select any of the plus indicators as appended to the end ofGame 001, Game 002 or Game 003 in order to add an additional game thatwould lead into each of these games. Thus, for example, in response tothe user clicking on UI element 211, the user interface wouldautomatically update and refresh to add an additional game to the leftof Game 003 and introduce an additional round into the tournamentbracket. Thus, the new Game 009, for example, would then become the onlygame in Round 1 while the other games in Round 1 would become Round 2,the games in Round 2 would now be Round 3 and so forth. Thus, the usercan quickly add games and develop as many rounds as desired for thecurrent tournament bracket. Also shown in FIG. 2 is UI element 212 whichshows an X indicator connecting Game 003 to Game 004 between Round 1 andRound 2. By selecting or clicking on or otherwise interacting with thisUI element 212, the user can effectively remove Game 003 and any gamesthat lead into Game 003 from the tournament bracket. Thus, for example,if the user were to select the X indicator similar to UI element 212 atthe branch leading off of Game 008 in Round 4, then this would alsoremove, for example, Game 007 which leads into Game 008 and Game 005which leads into Game 007. Thus, the user has the option or the abilityto quickly remove entire sub-tournaments from the tournament bracket andmanage the tournament bracket in this way.

As will be described further with reference to FIGS. 5A and 5B, the usermay also be able to move games from one round to another round, suchthat the winner of a game might receive a bye from one round, skippingthe next round, and going onto the subsequent directly. This isillustrated in FIG. 2, for example, as the winner of Game 001 skipsRound 2 and goes straight to Round 3 to play in Game 006 against thewinner from Game 004 in Round 2. The user may be able to move thesegames from one round to another by, for example, clicking and draggingon a game to move it from one portion of the user interface to another,or in some instances, by touching and dragging an element from one roundto another round (e.g., when the user interface is displayed on a touchscreen device).

Each game in the tournament bracket may have associated with it variousattributes of the game, which inform the user about who is going to beplaying when and where. Further details about what each game shown inthe brackets may include is illustrated and described, for example, withreference to FIG. 8.

Also shown in FIG. 2 is UI element 203, which is a zoom level selectorwhich may be provided to enable the user to zoom in or out of thetournament bracket to view more or less detail about the tournament.This zoom feature may, for example, zoom out to show more games in oneview at a time so that the user can quickly scan the entire tournamentand figure out where teams will be progressing through the tournamentbrackets or to quickly jump from one section of the tournament toanother by zooming out and then zooming in on a different section of thetournament bracket. Although the example shown in FIG. 2 shows a zoomelement with a plus and minus icon and a sliding scale between, othervariations may also be used including a percentage number, a slidingscale bar and other similar type mechanisms which may be used to zoom inor out of the user interface.

FIGS. 3A and 3B illustrate an example of using the tournament bracketmanagement user interface to add a game or branch to a tournamentbracket in the SLA system 100 of FIG. 1. For example, the user maydynamically build a bracket by selecting the plus icons adjacent togames in the tournament bracket. The hand cursor pointing at UI element301 indicates that the user is selecting this UI element to add anadditional game off of this game in Round 1. The result of thisinteraction is shown in FIG. 3B. In FIG. 3B, the user interface has beenupdated to add Game 002 to the left and adjacent to the Game 001originally shown in FIG. 3A. The position of Game 002 in the userinterface may be relative to Game 001 such that there is still room tobranch off of Game 001 in another direction. Thus, for example, sinceGame 001 includes two different teams, the user may wish to branch offof Game 001 in two different directions, thus creating an additionalround before the Game 001 round. As shown in FIG. 3B, once the user hasselected the option to add an additional game, the user interfaceelement changes from the plus symbol to an X symbol as shown at UIelement 302. As discussed previously, this X symbol indicates that theuser may click on the X to remove the added game and return the userinterface to the view shown in FIG. 3A. Also shown in FIG. 3B, the newgame that has been added, Game 002, automatically adds the plusindicators to the left as shown at UI element 303 to enable the user toadd further games and additional rounds, preceding Game 002 in Round 1and Game 001 in Round 2. Thus, the user can continue to branch out thegames to as many levels as desired to fully develop or generate thetournament bracket.

FIGS. 4A and 4B illustrate an example of using the tournament bracketmanagement user interface to remove a game or branch from a tournamentbracket. Thus, for example, in FIG. 4A, UI element 401 is presented asan X symbol because there are games leading into the Round 3 of Game 008which may be removed by the user by selecting UI element 401. The resultof selecting UI element 401 is shown in FIG. 4B. FIG. 4B illustratesthat the entire branch of the tournament bracket which comprised Game007 and Game 005 has now been removed in its entirety. In someembodiments, the user interface may present a confirmation dialog to theuser to confirm the desire to remove an entire branch or a game beforeremoving the game. This may prevent the user from inadvertently removingeither a single game or a complicated branch of the tournament bracketaccidentally. As shown in FIG. 4B, the UI element 401 has been replacedwith UI element 402 which is the now familiar plus icon or symbolindicating that the user has the option to add an additional branch gameoff of Game 008 and build out a new branch if desired. Although notshown in FIGS. 4A and 4B, if a user removes a game or branch whichincludes one or more games in earlier rounds where there is only onegame in the round, then removal of the branch or game will result inremoval of the round as well. Thus, for example, if there were initiallyfour rounds and the removal of the branch in FIG. 4A were to remove theonly game from Round 1, then the resulting display in FIG. 4B would onlyshow three rounds.

FIGS. 5A and 5B illustrate an example of using the tournament bracketmanagement user interface to move a game or branch in a tournamentbracket in the SLA system 100 of FIG. 1. Thus, as shown in FIG. 5A, theuser element 501A corresponding to the Game 006 is being selected by theuser to move from Round 2 to Round 1. This will have the practicaleffect of granting the winner of game 6 a bye from Round 1 straight toRound 3, to play the winner of Game 007 from Round 2. The result of thisuser interaction is shown in FIG. 5B, wherein the user has completed theaction to move the game element 501A to Round 1, and the tournamentbracket user interface has been updated to reflect this move.

FIGS. 6A and 6B illustrate an example of using the tournament bracketmanagement user interface to add a team or placement to a game in atournament bracket. Thus, for example, starting with FIG. 6A thetournament bracket shown has already been configured to have the no. 1team in the division play the no. 2 team in the division in Game 001,and the no. 3 team in the division is going to play in Game 002 againsta team yet to be placed. Thus, the user may wish to add an additionaldivision placement team to Game 002 to play against the no. 3 team. Inthis example, the user is in the process of selecting the no. 6 team inthe division as shown at UI element 601A. FIG. 6B illustrates the resultof the user interaction started in FIG. 6A. Thus, at UI element 601B,the diagram shows that the user has selected the no. 6 team in thedivision and moved the selection over to Game 002. The user interactionmay be, for example, clicking on that element and dragging it into Game002 and releasing to end the drag operation. The drag and drop may beperformed, for example, by using a mouse on a computer or by a touch anddrag interaction supported on a touch-screen device or a similar userinteraction. Thus, by the examples shown in FIGS. 6A and 6B, the usercan quickly select division placements for the tournament bracket andbuild the tournament quickly. In other embodiments, the user may beselecting from the other placement menus, such as the flight placements,the bracket placements, the list of teams or the placement standingsoverall as discussed herein.

FIG. 7 illustrates an example user interface for dynamically generatingtwo or more tournament brackets. This figure shows multiple bracketsbeing added for the division, youth female age 6 through 7. Thus, asshown in FIG. 7, there is a first tournament 701 which is the “GoldLevel Tournament” and the second tournament bracket 702 which is namedthe “Silver Level Tournament.” Also shown in FIG. 7 is UI element 704,which is a horizontal variation on the zoom level selector 203illustrated and described with reference to FIG. 2. Also, as shown inthe “Brackets for Division” menu on the right, the bracket placementslist has been selected for expansion instead of the division placementslist. For each of the games presented in the two tournament brackets,the loser of each game is added to the list of potential bracketplacements that may be used to further generate or build the tournamentbracket.

In the example shown in FIG. 7, a silver level tournament has beenconstructed to have the losers of various games in the gold leveltournament play each other, presumably to play for a silver medal or asilver level ranking or placement score or similar consolation prize.Thus, for example, Game 004 has been set up to have the loser of Game001 from the gold level tournament bracket play the loser from Game 002,also from the gold level tournament bracket. In another embodiment notshown in FIG. 7, the user may also have the option to add a consolationgame to a tournament bracket which may enable the user to add anotherstand-alone game to a round and then have bracket placements placed intothat consolation game. Thus, for example, instead of having a silverlevel tournament bracket, as shown in FIG. 7, the user may simply have agold level tournament bracket and have the option to add a consolationgame, which may be, for example, a silver medal game where the losers ofGame 001 and Game 002 may play each other for the bronze medal.

FIG. 8 illustrates a detail view of a user interface element for a gamein a tournament which may be displayed as part of a tournament bracketmanagement user interface, involving a sport league administrationsystem, such as the sport league administration system of FIG. 1. Thegame UI element displays several attributes associated with the game.Thus, for example, UI element 801 indicates the name of the tournamentand/or game, as well as an identifier for the tournament game which maybe used for the bracket placements as described herein. A UI element 802provides an indicator of the first team that is going to play in thisgame. This may be a placement which may be an undetermined team at thepresent time, or it may be a particular team that the user has selectedfor this game. In some embodiments, the tournament game in a tournamentbracket will consist of two placement teams which will be determined asthe result of prior games played in preceding rounds (e.g., teamsplaying in a final round may be determined by the winners of gamesplayed in a semi-final round). But in some instances, the first roundgames may consist of placement teams which will not be known until thetime that the tournament is going to begin, since these placements mightbe, for example, based on division standings, flight standings or otherplacement standings which will be undetermined until the end of aseason. In one embodiment, the SLA system 100 may later populate thesegeneric team placement identifiers with the specific team names as gamescores and/or results are entered into the system and winning teams aredetermined.

Also shown in FIG. 8 at UI element 803, the game may include, forexample, information about the field or a particular venue that the gameis to be played. This may be shown by, for example, a drop-down list ormenu which might be user-selectable to change the field or it may be aread-only value which the user cannot change. This may be useful in thecontext of an automated scheduling system which automatically assignsfields to the games based on availability and based on timing. Thus, insome embodiments, the user may be able to override the field selectionor they may not.

FIG. 8 also includes UI element 804 which may illustrate to the user thedate and time that the tournament game is to be played. This may also beeither a read-only field or a user selectable and editable fielddepending on the embodiment. However, it should be clear that in mostinstances a tournament game in a later round should be played, or willbe played, at a date and time later than a game in a prior round. Thus,for example, if the winner of tournament Game 004 is to play in Game005, then it would make sense that Game 005 will have a date and timelater than the date and time of Game 004. However, in some instancesgames in earlier rounds may overlap with games in later rounds. Suchmight be the case if, for example, the game is a bye game.

Finally, in FIG. 8, UI element 805 indicates the other placement teamwhich is to be playing against the first placement team as indicated atUI element 802.

Examples of Methods for Generating Tournament Brackets

FIG. 9 schematically illustrates a logical flow diagram of an embodimentof a process 900 for building one or more tournament brackets andgenerating a tournament schedule in the SLA system 100 of FIG. 1. Theprocess 900 may be executed, for example, by the league managementmodule 110, the user interface module 130, the schedule managementmodule 120, and/or the tournament/bracket management module 125 of theSLA system 100 of FIG. 1. In one embodiment, the process 900 may also beexecuted in whole or in part by the user interface module 107 on a usercomputing device 105, in communication with the SLA system 100. Invarious embodiments, fewer blocks or additional blocks may be includedin the process, or various blocks may be performed in an order differentfrom that shown in FIG. 9. For ease of illustration, the process 900will be described as being executed by the SLA system 100.

Beginning at block 905, the SLA system 100 may access league and/or teamdivision data and game schedule data for a league division. For example,the league/team division data may be accessed from league data source140 and the game schedule data may be accessed from the game scheduledata store 150. The data may be used as part of the tournament bracketgeneration process, for example, by presenting a list of teams and/or alist of leagues in the user interface for selection to create atournament bracket. Similarly, the game schedule data may be used todetermine, in part, tournament bracket scheduling such as dates andtimes of the tournament bracket games as well as the fields and/orvenues that will be used for the various games in a tournament bracket.

At block 910, the SLA system 100 generates a tournament bracketmanagement user interface to display user configurable tournamentbrackets for the league division. An example of this user interface isshown, for example, in FIG. 2. The user interface may present variousoptions for the user to configure the tournament bracket including, butnot limited to, adding one or more brackets to a tournament, adding oneor more games to a tournament bracket including branching games off ofbase games in the tournament bracket and so forth, as discussed herein.

At block 915, the SLA system 100 receives user interaction input dataindicating a request to add, remove and/or move an expansion gamerelative to a base game. For example, a tournament bracket may beginwith a single game indicating the final round and the user may wish toadd additional rounds to the tournament bracket by adding one or moreexpansion games relative to the base game in the final round. The usermay do this, for example, by selecting the plus symbol or icon adjacentto the base game or by other interactions that may be supported by thetournament bracket management user interface. For example, in someembodiments, the tournament bracket user interface may support touchinputs or voice inputs and other types of user interaction inputs tofacilitate adding of brackets that may not necessitate clicking on anicon in the user interface.

At block 920, the tournament bracket interface is updated to add, removeor move the expansion game at a bracket branch position relative to thebase game. Thus, for example, in response to the user selecting to addan expansion game in a semi-final round, for example, the user interfaceconfiguration will update to add the additional round game such as theexample shown in FIGS. 3A and 3B. Also, in response to the userselecting the option to remove a game from the tournament bracket, theuser interface will update to remove that bracket, such as the exampleshown in FIGS. 4A and 4B. In another example, in response to the userselecting the option to move a game from one round to another round, theuser interface will update in response to the user interaction byupdating a display to show the relocated game in its new bracket round.This may be seen, for example in FIGS. 5A and 5B.

At block 925, the SLA system 100 checks to see if the user is stillconfiguring the tournament brackets. For example, the user interface mayprovide a user-selectable element, such as a button or link, which theuser may select to save the tournament bracket or otherwise end aconfiguration session. In another embodiment, the SLA system 100 maydetermine the user has finished configuring the tournament brackets inresponse to the user navigating away from the tournament bracketmanagement user interface or similar action such as logging out of theSLA system 100 or otherwise ending a user session. If the user is stillconfiguring the tournament brackets, the process may return to block 915and receive additional user interaction input data indicating furtherrequests to update the tournament bracket by adding, removing or movinggames. Thus, the process for blocks 915, 920 and 925 may continue torepeat an indeterminate or iterative number of times as the usercontinues to build the tournament bracket. Once the user is finishedconfiguring the tournament brackets, the process can proceed to block930.

At block 930, the SLA system 100 constructs or updates the bracket gameconfiguration based on the tournament bracket user interfaceconfiguration. Thus, for example, if the user has built a tournamentbracket consisting of three rounds and eight games, then the bracketgame configuration will be constructed to match the user interfacesettings as constructed by the user. This would include which winner ofeach game plays the next winner of the next game, which teams orplacements play in the first round of games and against who, as well asconfiguration data for the field and/or venue, the date and time andother such information as needed to set up each game in the tournamentbracket.

At block 935, the SLA system 100 generates the tournament bracket forthe selected league division based on the constructed bracketconfiguration. This tournament bracket may be stored in, for example,the game and schedule data store 150 for later use and access in eithergenerating a user interface view of the tournament bracket for an enduser who wishes to view the tournament schedule or for later use by theleague administrator to continue editing or working on the tournamentbracket. In some embodiments, the generated tournament brackets may alsobe saved by the administrator or user for later use as a template. Thus,a tournament bracket template library may be built up or accumulatedover time which may include a library of commonly used tournamentbrackets or tournament configurations. These may be quickly accessed bythe administrator for re-use in another tournament bracket, in adifferent division, and so on. Such saved templates or libraries may bestored, for example, in the league data store 140 and/or thegame/schedule data store 150.

FIG. 10 schematically illustrates a logical flow diagram of anembodiment of a process 1000 for configuring one or more tournamentbrackets and generating a tournament schedule in SLA system 100 ofFIG. 1. The process 1000 may be executed, for example, by the leaguemanagement module 110, the user interface module 130, the schedulemanagement module 120, and/or the tournament/bracket management module125 of the SLA system 100 of FIG. 1. In one embodiment, the process 1000may also be executed in whole or in part by the user interface module107 on a user computing device 105, in communication with the SLA system100. In various embodiments, fewer blocks or additional blocks may beincluded in the process, or various blocks may be performed in an orderdifferent from that shown in FIG. 10. For ease of illustration, theprocess 1000 will be described as being executed by the SLA system 100.

Beginning at block 1005, the SLA system 100 accesses the league/teamdivision data and game schedule data for a league division. For example,the league/team division data may be accessed from league data source140 and the game schedule data may be accessed from the game scheduledata store 150. The data may be used as part of the tournament bracketgeneration process, for example, by presenting a list of teams and/or alist of leagues in a user interface for selection to create a tournamentbracket. Similarly, the game schedule data may be used to determine, inpart, tournament bracket scheduling such as dates and times of thetournament bracket games as well as the fields and/or venues that willbe used for the various games in a tournament bracket.

At block 1010, the SLA system 100 can generate the tournament bracketmanagement user interface to display user configurable tournamentbrackets for the league division. An example of this user interface isshown, for example, in FIG. 2. The user interface may present variousoptions for the user to configure the tournament bracket including, butnot limited to, adding one or more brackets to a tournament, adding oneor more games to a tournament bracket, branching games off of base gamesin the tournament bracket, and so forth, as discussed herein.

At block 1015, the SLA system 100 receives user interaction input data,such as a drag and drop operation, indicative of a request to add a teamplacement to a select game. For example, the process is similar to theone shown in FIG. 6A, 6B. Thus, the user may drag and drop a divisionplacement, a flight placement, a bracket placement, a specific team or aplacement by overall score into the games in the tournament bracket.

At block 1020, the SLA system 100 updates the tournament bracket userinterface to add the team placement to the selected game. For example,the selected game would be updated to show the placement or team addedto the game, either on the top or the bottom of the game.

At block 1025, the SLA system 100 detects or determines whether the useris still configuring the tournament brackets (e.g., similar to thedescription of block 925 of FIG. 9), and if so, the process may returnto block 1015 to receive additional user interaction input as describedabove. Thus, the process may repeat blocks 1015, 1020 and 1025 anindeterminate number of times as the user continues to build the teamplacements for the tournament bracket.

Once the user has completed or has finished configuring a tournamentbracket, then at block 1030 the SLA system 100 can construct or updatethe bracket game configuration based on the team placements in the userinterface. The process at block 1030 is similar to the one describedwith reference block 930 of FIG. 9.

At block 1035, the SLA system 100 generates the tournament bracket forthe selected league division based on the constructed bracket hierarchy.The process at block 1035 is similar to the one described with referenceblock 935 of FIG. 9.

Additional Embodiments

In general, any of the routines, processes, methods or criteriadisclosed herein for dynamic generation of tournament brackets can beused individually or in combination with any of the other routines,processes, methods or criteria disclosed herein.

In some embodiments, the SLA system 100 may be configured differently,include different components or modules, and/or omit some components ormodules shown in FIG. 1. For example, in one embodiment, SLA system 100includes one or more hardware processors in communication with acomputer readable medium storing software modules including instructionsthat are executable by the one or more hardware processors, and one ormore software modules. The one or more hardware processors may include,for example, digital logic circuitry. The one or more software modulesmay instruct a computing system to execute the various methods,approaches, and/or techniques as described herein.

As described above, the SLA system 100 can be implemented by a computingsystem that includes one or more physical servers or other computingmachines, such as several computing machines interconnected via anetwork. Thus, each of the components depicted in the SLA system 100 caninclude hardware and/or software for performing various features. In oneembodiment, the SLA system 100 is implemented in association with a website or collection of web sites. Various disclosed features can beincorporated into a mobile device operating system, a mobileapplication, a sport league administration site or service, a socialnetworking service, or any combination of these.

The SLA system 100 can include one or more servers for receiving andresponding to network requests from the user computing device(s) 105.The one or more servers can include web servers, application servers,database servers, combinations of the same, or the like. In someembodiments, the network 160 is a publicly accessible network of linkednetworks, possibly operated by various distinct parties, such as theInternet. In other embodiments, the network 160 may be a privatenetwork, such as, for example, a corporate or university network that iswholly or partially inaccessible to non-privileged users. In still otherembodiments, the network 160 may include one or more private networkswith access to and/or from the Internet. User computing devices 105 maybe any type of personal computer or mobile computing device (such as asmart phone, tablet, electronic book reader, or any other type ofportable computing device).

The processing of the various components of the SLA system 100 can bedistributed across multiple machines, networks, and other computingresources. The various components of the SLA system 100 can also beimplemented in one or more virtual machines, rather than in dedicatedservers. Likewise, the data repositories shown can represent physicaland/or logical data storage, including, for example, storage areanetworks or other distributed storage systems. Moreover, in someembodiments the connections between the components shown representpossible paths of data flow, rather than actual connections betweenhardware. While some examples of possible connections are shown, any ofthe subset of the components shown can communicate with any other subsetof components in various implementations.

In some embodiments, the SLA system 100 may be configured differentlythan illustrated in the figures above. For example, variousfunctionalities provided by the illustrated modules can be combined,rearranged, added, or deleted. In some embodiments, additional ordifferent processors or modules may perform some or all of thefunctionalities described with reference to the example embodimentillustrated in the figures above. Many implementation variations arepossible.

In some embodiments, the SLA system 100 may be implemented on, or incommunication with, one or more hosted computing environments. Thehosted computing environments may include a collection of rapidlyprovisioned and released computing resources hosted in connection withthe SLA system 100. Such computing resources may be referred to,individually, as host computing devices. The computing resources mayfurther include a number of computing, networking and storage devices incommunication with one another. In some embodiments, the computingdevices may correspond to physical computing devices. In otherembodiments, the computing devices may correspond to virtual machineinstances implemented by one or more physical computing devices. Instill other embodiments, computing devices may correspond to bothvirtual computing devices and physical computing devices. A hostedcomputing environment may also be referred to as a cloud computingenvironment.

Each of the processes, methods, and algorithms described in thepreceding sections may be embodied in, and fully or partially automatedby, code modules executed by one or more computers, computer processors,or machines configured to execute computer instructions. The codemodules may be stored on any type of non-transitory computer-readablemedium or tangible computer storage device, such as hard drives, solidstate memory, optical disc, and/or the like. The processes andalgorithms may be implemented partially or wholly inapplication-specific circuitry. The results of the disclosed processesand process steps may be stored, persistently or otherwise, in any typeof non-transitory computer storage such as, e.g., volatile ornon-volatile storage.

CONCLUSION

Depending on the embodiment, certain acts, events, or functions of anyof the processes or algorithms described herein can be performed in adifferent sequence, can be added, merged, or left out altogether (e.g.,not all described operations or events are necessary for the practice ofthe algorithm). Moreover, in certain embodiments, operations or eventscan be performed concurrently, e.g., through multi-threaded processing,interrupt processing, or multiple processors or processor cores or onother parallel architectures, rather than sequentially.

Conditional language used herein, such as, among others, “can,” “could,”“might,” “may,” “e.g.,” and the like, unless specifically statedotherwise, or otherwise understood within the context as used, isgenerally intended to convey that certain embodiments include, whileother embodiments do not include, certain features, elements and/orsteps. Thus, such conditional language is not generally intended toimply that features, elements and/or steps are in any way required forone or more embodiments or that one or more embodiments necessarilyinclude logic for deciding, with or without author input or prompting,whether these features, elements and/or steps are included or are to beperformed in any particular embodiment. The terms “comprising,”“including,” “having,” and the like are synonymous and are usedinclusively, in an open-ended fashion, and do not exclude additionalelements, features, acts, operations and so forth. Also, the term “or”is used in its inclusive sense (and not in its exclusive sense) so thatwhen used, for example, to connect a list of elements, the term “or”means one, some, or all of the elements in the list.

Disjunctive language such as the phrase “at least one of X, Y, and Z,”unless specifically stated otherwise, is otherwise understood with thecontext as used in general to present that an item, term, etc., may beeither X, Y, or Z, or any combination thereof (e.g., X, Y, and/or Z).Thus, such disjunctive language is not generally intended to, and shouldnot, imply that certain embodiments require at least one of X, at leastone of Y, and at least one of Z.

While the above detailed description has shown, described and pointedout novel features as applied to various embodiments, it can beunderstood that various omissions, substitutions and changes in the formand details of the devices or algorithms illustrated can be made withoutdeparting from the spirit of the disclosure. As can be recognized,certain embodiments described herein can be embodied within a form thatdoes not provide all of the features and benefits set forth herein, assome features can be used or practiced separately from others. The scopeof certain embodiments disclosed herein is indicated by the appendedclaims rather than by the foregoing description. All changes that comewithin the meaning and range of equivalency of the claims are to beembraced within their scope.

What is claimed is:
 1. Non-transitory computer storage which stores executable program instructions that direct a computing system comprising one or more computing devices to perform a process that comprises: accessing tournament data for a tournament, including bracket data for a tournament bracket; generating, for display on a computing device, a tournament bracket user interface including at least a tournament bracket visualization element, the tournament bracket visualization element configured to display the tournament bracket as a tree diagram, wherein the tournament bracket comprises one or more games, wherein at least one game is displayed with a user-selectable element enabling an administrator to dynamically add one or more new games to the tournament bracket after the tournament bracket visualization element is configured; receiving user interaction input data for a user interaction indicative of a request to add a new game relative to a base game in the tournament bracket visualization element; updating, based on the user interaction input data, the tournament bracket visualization element to add, to the tournament bracket user interface, the new game as a branch in the tree diagram relative to the base game, wherein the new game precedes the base game in the tournament bracket; and generating a tournament schedule based on the updated tournament bracket, wherein the tournament schedule is configured to be updated automatically in response to updates to tournament data without requiring further input from the administrator.
 2. The non-transitory computer-readable storage of claim 1, wherein the tournament bracket visualization element is configured to display two or more tournament brackets for the tournament.
 3. The non-transitory computer-readable storage of claim 1, wherein at least one game is displayed with a second user-selectable element enabling the administrator to remove one or more existing games from the tournament bracket, and wherein the process further comprises: receiving user interaction input data for a user interaction indicative of a request to remove an existing game relative to a base game in the tournament bracket; and updating, based on the user interaction input data, the tournament bracket visualization element to remove, from the tournament bracket user interface, the existing game and an existing branch in the tree diagram based on the existing game being removed.
 4. The non-transitory computer-readable storage of claim 1, wherein at least one game is a user-selectable candidate game to enable the administrator to move the candidate game from an initial round to a destination round in the tournament bracket, and wherein the process further comprises: receiving user interaction input data for a user interaction indicative of a request to move the candidate game from the initial round to the destination round in the tournament bracket; and updating, based on the user interaction input data, the tournament bracket visualization element to display the candidate game in the destination round in the tournament bracket.
 5. The non-transitory computer-readable storage of claim 1, wherein generating the tournament schedule based on the updated tournament bracket user interface further comprises: determining, based on field availability data associated with the accessed tournament data, a playing field for each game in the tournament bracket; assigning, based on team placement data associated with the accessed tournament data, playing teams for at least the first round of games in the tournament bracket; determining, based on team schedule data associated with the accessed tournament data and on the tournament bracket configuration, a playing date and time for each game in the tournament bracket; and assigning the determined playing field and determined playing date and time to each respective game in the tournament bracket.
 6. The non-transitory computer-readable storage of claim 1, wherein the tournament bracket user interface further includes a bracket configuration menu display element, and wherein the bracket configuration menu display element includes a user-selectable list of one or more divisions, a user-selectable list of one or more division placements associated with a selected division, a user-selectable list of one or more teams associated with a selected division, and a user-selectable list of bracket placements associated with the tournament bracket.
 7. The non-transitory computer-readable storage of claim 6, wherein the process further comprises: receiving user interaction input data for a user interaction indicative of a request to add, to a target game in the tournament bracket, a division placement, a team, or a bracket placement; and updating the tournament bracket visualization element to display the division placement, the team, or the bracket placement as a competitor in the target game.
 8. The non-transitory computer-readable storage of claim 7, wherein the user interaction is a drag and drop operation performed by the administrator via a computer user input device.
 9. The non-transitory computer-readable storage of claim 8, wherein the computer user input device is a mouse or a touch-screen enabled display.
 10. The non-transitory computer-readable storage of claim 1, wherein the instructions are instructions of a mobile device application.
 11. A computing system comprising: a data store configured to store tournament data for one or more tournaments; one or more processors; and a user interface module executable on the one or more processors, the user interface module configured to at least: access, from the data store, tournament data for a tournament, the tournament data including bracket data for a tournament bracket associated with the tournament; generate a tournament bracket user interface, including at least a tournament bracket visualization element, the tournament bracket visualization element configured to initialize and display the tournament bracket for as a tree diagram, wherein the tournament bracket comprises one or more games, wherein at least one game is displayed with a user-selectable element enabling an administrator to add one or more new games to the tournament bracket after the tournament bracket visualization element is initialized; wherein the tournament bracket user interface is configured to: receive user interaction input data for a user interaction indicative of a request to add a new game relative to a base game in the tournament bracket visualization element; and update, based on the user interaction input data, the tournament bracket visualization element to add, to the tournament bracket user interface, the new game as a branch in the tree diagram relative to the base game, wherein the new game precedes the base game in the tournament bracket; and a scheduling module executable on the one or more processors, the scheduling module configured to at least: receive, via the tournament bracket user interface, tournament bracket configuration data; and generate a tournament schedule for the tournament based on the tournament bracket configuration data, wherein the tournament schedule is configured to be updated automatically by the scheduling module in response to updates to the tournament data without requiring further input from the administrator.
 12. The computing system of claim 11, wherein to automatically generate the tournament schedule, the scheduling module is further configured to: determine, based on field availability data associated with the accessed tournament data, a playing field for each game in the tournament bracket; assign, based on team placement data associated with the accessed tournament data, playing teams for at least the first round of games in the tournament bracket; determine, based on team schedule data associated with the accessed tournament data and on the tournament bracket configuration, a playing date and time for each game in the tournament bracket; and assign the determined playing field and determined playing date and time to each respective game in the tournament bracket.
 13. The computing system of claim 11, wherein the tournament bracket user interface further includes a bracket configuration menu display element, and wherein the bracket configuration menu display element includes a user-selectable list of one or more divisions, a user-selectable list of one or more division placements associated with a selected division, a user-selectable list of one or more teams associated with a selected division, and a user-selectable list of bracket placements associated with the tournament bracket.
 14. The computing system of claim 11, wherein the computing system is a mobile computing device.
 15. The computing system of claim 11, wherein the computing system is a web server.
 16. A computerized method for enabling a tournament organizer to dynamically generate a tournament bracket, the computerized method comprising: accessing tournament data for a tournament; generating, for display on a computing device, a tournament management user interface including at least a bracket visualization element, the bracket visualization element configured to initialize and display a bracket for the tournament as a tree diagram, wherein the bracket comprises one or more games, wherein at least one game is displayed with a user-selectable element enabling a tournament organizer to add one or more new games to the bracket after the bracket is initialized; receiving user interaction input data for a user interaction indicative of a request to add a new game relative to a base game in the bracket; updating, based on the user interaction input data, the bracket visualization element to add, to the bracket user interface, the new game as a branch in the tree diagram relative to the base game, wherein the new game precedes the base game in the bracket; and automatically generating a tournament schedule for the tournament based on the updated bracket user interlace, wherein the method is performed by a computing system comprising one or more computing devices.
 17. The method of claim 16, wherein at least one game is displayed with a second user-selectable element enabling the tournament organizer to remove one or more existing games from the bracket, and wherein the method further comprises: receiving user interaction input data for a user interaction indicative of a request to remove an existing game relative to a base game in the bracket; and updating, based on the user interaction input data, the bracket visualization element to remove, from the bracket user interface, the existing game and an existing branch in the tree diagram based on the existing game being removed.
 18. The method of claim 16, wherein at least one game is a user-selectable candidate game to enable the tournament organizer to move the candidate game from an initial round to a destination round in the bracket, and wherein the method further comprises: receiving user interaction input data for a user interaction indicative of a request to move the candidate game from the initial round to the destination round in the bracket; and updating, based on the user interaction input data, the bracket visualization element to display the candidate game in the destination round in the bracket.
 19. The method of claim 16, wherein the bracket user interface further includes a bracket configuration menu display element, and wherein the bracket configuration menu display element includes a user-selectable list of one or more divisions for the tournament, a user-selectable list of one or more division placements associated with a selected division, a user-selectable list of one or more teams associated with a selected division, and a user-selectable list of bracket placements associated with the bracket.
 20. The method of claim 16, further comprising: receiving user interaction input data for a user interaction indicative of a request to add to a target game in the bracket a division placement, a team, or a bracket placement; and updating the bracket visualization element to display the division placement, the team, or the bracket placement as a competitor in the target game. 